Refresh the Studio screenshots after the Monitoring and instance rebuilds - #82
Open
rnv812 wants to merge 4 commits into
Open
Refresh the Studio screenshots after the Monitoring and instance rebuilds#82rnv812 wants to merge 4 commits into
rnv812 wants to merge 4 commits into
Conversation
The 2.7.0 post illustrated itself from public/images/studio_ui, which the documentation reshoots whenever Studio changes. Its two images move under public/images/blog/eventum-2-7-0, where the release keeps them as the record of what shipped.
Every screenshot on the site dated from before the rebuilds of Monitoring and the instance page, the identity plate of Management, the log channels, project import and export, and the Repositories section the left rail has gained since - so every full page shot was of an interface no longer there. All 33 screens are shot again, light and dark, from one instance: a workspace of eighteen projects, sixteen instances across every state, two scenarios exchanging global state through templates and a script, a repository connected and a generator installed from it, and an hour of generation behind the charts.
Monitoring opens on one line of state rather than a row of stage totals, holds a window of 2.5, 10 or 30 minutes, and gathers the running instances into one section - a load chart split by instance or by stage, quick filters and a search that narrow it with the table, and a row that opens the details of that instance. The instance overview leads with what the run costs, and keeps its throughput, its pipeline and what the instance is in one column each. Home sends you to Repositories in place of the Hub, the application log is split into channels, and the events queue can be bounded in memory.
Read against the shots they replaced, seven of them said less than before: the repository was closed over its catalog, the inspector stood on a stage with one plugin instead of the four the page describes, the formatter had nothing for its errors panel to report, an instance carried no parameters, the queue estimate and the data flow diagram had scrolled out of frame, and a scenario had lost a member.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #74.
Every screenshot on the site was taken before the rebuilds of Monitoring and the instance page, the identity plate of Management, the log channels, project import and export, and the Repositories entry the left rail has gained since — so every full-page shot documented an interface that is no longer there.
Screenshots
All 33 screens are shot again, light and dark, at 1920x1080 — 27 under
studio_ui/and 6 underhome/, the last of which the landing page and the feature tour read.The scope is wider than the issue's table on purpose: the left rail gained Repositories, and it is in every full-page shot, so a selective reshoot would have left the rest visibly older than the pages beside them.
scenario_*were stale for a second reason the issue does not name — the data flow diagram is built from scripts as well as templates now — andrepositories_*predated Discover and the paging under it by a few hours.They come from one staged instance, so the screens agree with each other: eighteen projects, sixteen instances across every state, two scenarios exchanging four global keys through templates and a
scriptevent plugin, a repository connected with a generator installed from it, six secrets in the keyring, and an hour of generation behind the charts and the failure counts.The release post
The 2.7.0 post illustrated itself from
studio_ui/, which this reshoot rewrites. Its two images are now its own, underpublic/images/blog/eventum-2-7-0/, the way the 2.4.0 post already keeps them — a release post stays a record of that release.Prose
A stale sentence is worse than a stale image, so the pages were read against the instance rather than only re-illustrated:
pnpm buildpasses.Out of scope
eventum-generator/eventumis the same shot; it ships in a PR of that repository.0 keyswhile the API already holds them. The screenshot was taken with its own refresh pressed; the fix belongs in its own issue.